home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
cyb02pdc.zip
/
CYB02PDC.TTY
< prev
next >
Wrap
Text File
|
1992-07-23
|
8KB
|
164 lines
▓▓▓▓▓▒ ▓▓▒ ▓▓▒ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓▒ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓ ▓▓▓▓▓▓▓ ▓▓▓▓▓▒
▓▒▒▒▒▒░ ▓▒░ ▓▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒░
▓▒▒░░░░░ ▓▒░ ▓▒░ ▓▒░░░░▒▒░ ▓▒▒░░░░░░ ▓▒░░░░▒▒░ ▓▒░░░░▒▒░ ▓▒░░░░▒▒░ ▓▒▒░░░░░
▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░
▓▒░ ▓▒▒▓▓▓▒▒░ ▓▒▒▓▓▓▒▒░ ▓▒▒▓▓▓▓▒ ▓▒▒▓▓▓▒▒░ ▓▒▒▓▓▓▒▒░ ▓▒░ ▓▒░ ▓▒░
▓▒░ ▓▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒░ ▓▒░ ▓▒░
▓▒░ ▓▓▒░░ ▓▒░░░░▒▒░ ▓▒░░░░░░ ▓▒░░░▒▒▒ ▓▒░░░░░ ▓▒░ ▓▒░ ▓▒░
▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒░
▓▒▒▓▓▓▓▒ ▓▒░ ▓▒▒▓▓▓▒▒░ ▓▒▒▓▓▓▓▓▒ ▓▒░ ▓▒░ ▓▒░ ▓▒▒▓▓▓▒▒░ ▓▒▒▓▓▓▓▒
▓▒▒▒▒▒░ ▓▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒▒░ ▓▒░ ▓▒░ ▓▒░ ▓▒▒▒▒▒▒░ ▓▒▒▒▒▒░
░░░░░░ ▒░░ ▒░░░░░░ ░░░░░░░ ▒░░ ▒░░ ▒░░ ▒░░░░░░ ░░░░░░
P C B o a r d ( F i l e ) D e s c r i p t i o n C o m p r e s s o r
Version 2.00112ß (c) Copyright <<> westsmith 92/7/23
The FlatEarth BBS, CyberNET 1:416/803.0,804.0
──────────────────────────────────────────────────────────────────────▄▄▄▄▄▄▄▄
┌─┐ CYBERPDC
└─┘ PCBoard (File) Description Compressor
It is not rare to find that user-entered file descriptions, and DIZ files
themselves, don't use the full 45 column default width that PCBoard allows
for file information. Directory listings can usually be compressed into
fewer lines by removing extra spaces in the descriptions. This means fewer
screens of data for users to wade through, and a more efficient and
uniform appearance for the file data.
PDC.EXE reads in a PCBoard directory file (that uses default spacing) and
breaks up the descriptions, writing them to a target file using as few
lines as possible without actually changing the words of the text.
──────────────────────────────────────────────────────────────────────▄▄▄▄▄▄▄▄
┌─┐ FILES
└─┘ Names and Descriptions, FoxPro Information
pdc.exe 45,287 : CYBERPDC 2.00112ß PCBoard (File) Desc. Compressor
pdc.bas 8,673 : Microsoft QuickBASIC 4.0 source code for PDC.EXE
pdc.prg 4,252 : FoxPro 2.0 source code for PDC.EXE
browse.prg 70 : FoxPro 2.0 program "do browse," reads FOXDIR.DBF
pcbdir.dbf 193 : FoxPro 2.0 database, interim step
foxdir.dbf 225 : FoxPro 2.0 database, final product
foxdir.fpt 512 : FoxPro 2.0 memo fields for FOXDIR.DBF
cyb02pdc.tty 8,153 : This document
The only file actually required for CYBERPDC to run is PDC.EXE. I would
also recommend that you keep a copy of this document until you've read it
and are comfortable with the utility.
The second group of files are essentially a non-compiled version of the
same program, but written in Fox (Microsoft now?) Software's FoxPro 2.00.
While PDC.PRG should port to any xBase-standard dialect², the DBFs don't
seem to be completely compatible. If you're trying to port out of Fox
and can't read the DBF's, you can re-create them:
Structure for database: C:\SUB\CYB02PDC\PCBDIR.DBF
Number of data records: 0
Date of last update : 07/23/92
Field Field Name Type Width Dec Index
1 FILE Character 13
2 SIZE Numeric 8
3 DATE Character 10
4 P Character 2
5 DESC Character 45
** Total ** 79
Structure for database: C:\SUB\CYB02PDC\FOXDIR.DBF
Number of data records: 0
Date of last update : 07/23/92
Memo file block size : 64
Field Field Name Type Width Dec Index
1 NAME Character 8
2 EXT Character 3
3 SIZE Numeric 8
4 DATE Date 8
5 DESC Memo 10
6 UPLOADER Character 32
** Total ** 70
Additionally, you'll likely have a problem with the extended switches
in BROWSE.PRG if you try to run it outside of FoxPro. The second-to-last
field element is a temporary detail on the first line of the memo field
attached to each file-record.
The FoxPro code is significantly slower than its Microsoft QuickBASIC
counterpart. Because of this, and because a user's likely destination in
FoxPro will be to generate a DBF file from the PCBoard directory, I did
not include a routine in PDC.PRG to write back a compressed PCB DIR.
² - I've made brief use of FoxPro's windowing system. There are two
calls in the main body of the code, and another in the HURL
procedure. To port out of Fox, you'll need to change these as
your chosen dialect allows.
──────────────────────────────────────────────────────────────────────▄▄▄▄▄▄▄▄
┌─┐ HISTORY
└─┘ Version List, Bug Fixes
92/07/20 - Original Release.
CYBERPDC
1.00263ß CYBER???'s are built on a standard program frame that I drew
up over a year ago. Some portions of the code may seem a bit
overdone or unnecessary; most of the routines were designed to
be flexible and handle whatever was required for each different
utility.
After spending a year and a half freely trading utilities and
code with other Telegard BBS users and the Fido community, I was
rather shocked upon entering the PCBoard arena to find that it
seems to lack entirely a "support," community.
Everyone and their dog has written something for PCBoard, but
most tools are crippled, encrypted and released without source.
There seems to be more emphasis on turning a buck than rolling
the computer-wheel out of the stone age. It's not uncommon to
find a dozen utilities for PCBoard with precisely the same
purpose, each crippled until users send in $20, coded very
likely because each new author didn't want to send in $20 the
the last guy.
For major software efforts, charging (reasonable) rates is
unavoidable (although counter-evolutionary, silicon-wise).
For small stuff that someone burns out in a day or 3, charging
register cash is petty and not at all conducive towards
encouraging people to use the work.
The result seems to be a lot of developers starting from
Ground-Zero all the time. Disappointing, to say the least.
CYBERPDC.EXE is hardly rocket science, but if anyone can make
use of the code and go a step further, go for it. I'd appreciate
only a copy of your program and perhaps notice for having coded
the original few lines.
92/07/23 - Bug Fix. Discovered (too late) that the "Uploaded by:" exception
2.00112ß processing wasn't working properly. The read cycle collects
CYB02PDC description data until encountering EOF or the next filename,
before finally reducing and printing off to file. The check for
"Uploaded by:" on the other hand, was tossing off a line to
output as soon as it was found. File blocks were coming out with
the "Uploaded by: " line first, then the file specs, and finally
the descriptions.
A few lines from the standard frame (see Original Release) were
removed to free up a bit more memory.
92/07/23 - Parallel code written in FoxPro 2.0. PDC.PRG will generate a
2.00113ß DBF (and memo composite) from a PCBoard directory, instead of
CYB02PDC another compressed PCB DIR file.
- fin -